Experiment with job-context action
#3
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Noticed that you can use |
omus
changed the title
job-name actionjob-context action
|
Superseded by beacon-biosignals/job-context#1 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Prototyping a new GHA
job-contextwhich is meant for determining the job name and id which are things both not available via GHA contexts.In particular this actions allows runnings jobs to determine their own job name and job ID which is useful when interacting with the GitHub API. The intent is to use this action so that the
matrix-outputjob can include the job ID as part of the artifact name.One relevant implementation detail is that this action makes use of multiple GitHub contexts in order to generate the job name. Without these contexts we couldn't fill in the allows GitHub expressions which can be present in a job name. If we could solve this problem in another way we may be able to allow the use of a user specified job key.